home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Atari Mega Archive 1
/
Atari Mega Archive - Volume 1.iso
/
lists
/
gem
/
l_0799
/
504
< prev
next >
Wrap
Internet Message Format
|
1994-08-27
|
5KB
Date: Wed, 22 Jun 94 13:36 CDT
From: ekl@sdf.lonestar.org (Evan K. Langlois)
To: gem-list@world.std.com
Subject: Re: A Proposal For Everyone
Precedence: bulk
========================================================================
First, as I said before, ^W for close window does not make anymore sense
than ^W for cycle windows. The only thing is that all programs in Germany
already use ^U for closing a window - you better wake up and check the
German ftp sites - they are VERY consistent. Atari and SDS were a bit late
and so are you.
========================================================================
And does ^U make any more sense for closing a widow? Does it?
My point is that ^U is arbitrary. I have two official documents that
name ^w for closing a window. The ATARI Compendium (which takes the
info right out of ATARI MultiTOS User Interface Guidelines, c. ATARI 1992)
and the NeXT Guidelines. I think Apple uses this too. Why make ATARI
different? For Germany? I don't give a damn about what Germany says.
I don't live their and don't own their software. What will underline
be if ^U is for closing a window? ATARI says ^U is underline, which DOES
make sense.
========================================================================
>Command-h Hide File
>^ tab Cycle Object Selection <<no menu>>
>Command-e Enter Selection Edit
What do these mean?
========================================================================
Uhh .. I actually don't know about ^h and ^e, again I simply copied
over the NeXT guidelines word for word, and changed it to match the ATARI
guidelines (almost NO changes neces And then added in your last
proposal.
I think ^h may be to hide the currently selected object, such as if a
ruler is selected, or a set of tools.
Uhh .. I think ^e means to enter the selected object (or text) at the
current cursor position. I'm not sure I don't have a next. Drop these
if you like. They aren't needed.
As for the use of lower case, I thought that would save some room on the
menus, but I guess their is something confusing about lower case. drop
it.
ATARI says in object oriented apps, TAB should be used to deselect the
current object and select the next one. I figures ^TAB may be better, much
like the way some dialog handlers use TAB to go to the next selection.
I was kinda reaching though. Go ahead and drop it.
========================================================================
>SHIFT-tab Cycle Windows Window
Shift Tab is already in use as backtab.
========================================================================
OK, how about shift-tab for backtab, and ^tab for cycle windows? or
is that bad too? TAB could stay as cycle object for object based apps
and non-text apps. Shift-tab for reverse cycle (of objects in non-text
apps) and shift ^ tab for reverse cycle windows?
Will that do?
========================================================================
>Command-d Find Previous Edit
This is not bad, honest. But I thing the Shift+CTRL+G method makes more
sense in the context of the new standard.
========================================================================
Hmm .. I kinda like ^d because its easy (no shift keys) and finding a next
isn't really the opposite of finding previous. If you look at the position
of the keys, its really nice. ^f for find in the middle. The "next"
key (position wise) is ^g for find next. And teh previous key is ^d for
find previous. That makes ALOT of sense to me, and again its a NeXT
standard. However, ATARI doesn't define find next OR find previous, so
they aren't gonna back me up here :-)
I think the whole reason for ^g in the first place was because of position.
Adapting find previous for the same reason seems very logical.
========================================================================
I believe that my proposal manages to find a compromise by assigning ^Tab
to cycle windows which makes perfect sense and ^Esc for closing while
maintaining compatibility with the German standard.
========================================================================
OK, we agree on ^TAB. But I thought you wanted ^U for Window Close?
^ ESC is really out there. I don't know. Maybe, but I don't any reason
to change ^W or have multiple short-cuts for one function.
========================================================================
I'll be happy to do it myself, I just thought you did a very good job of
dividing the commands into categories. If you don't want to, I'll do it
myself.
========================================================================
I didn't!!! Did you read the NeXT Guidelines? They were posted to this
list (I don't know by who), but I saved them, and when I read through
them and found they coincided with the ATARI Guidelines almost exactly
I merged 'em. The categories are NeXT's idea.
I'll make the changes the my end for the TAB differences. And remove ^e.
Should ^h (HIDE) be removed? I'd like to keep ^d and ^w though.
What is the current agreement (or lack thereof) on ^a and S^a?
Oh, thanks for being specific this time. We'll never agree on anything
at all unless you site specific thiongs that you dislike.
========================================================================
>SHIFT-tab Cycle Windows Window
Shift Tab is already in use as backtab.